|
|
 |
|
|
|
|
1. What are two ways you can structure an iteration plan? |
|
|
|
|
|
|
|
|
If you choose the Objectory Process (the official UML process), analysis, design, and construction can be decomposed into iterations, with one or more increments per iteration. |
|
|
|
|
|
|
|
|
2. What are the benefits of revisiting your use cases? |
|
|
|
|
|
|
|
|
Revisiting use cases helps to continually verify that the system is still on track to fulfill the requirements or user expectations of the Visual Basic application. This revisitation also helps to ensure that the use case model remains robust and easily extensible as discoveries about the problem and solution are made. Always keep in mind that the importance of updating the content of the use cases is that the use case model not only defines the behavior of the application but also provides a basis for the development process of your project itself. |
|
|
|
|
|
|
|
|
3. Why is it important to involve your users in the refining of your use cases? |
|
|
|
|
|
|
|
|
Involving users in the refining of your use cases and sequence diagrams goes a long way toward filling in gaps in business activities you've modeled. Users also help to validate your assumptions about how your Visual Basic application will solve their problems. At the end of each iteration, you should plan on user review and testing. |
|
|
|
|
|
|
|
|
4. Explain the financial implications of elaborating business processes while developing your applications. |
|
|
|
|
|
|
|
|
The development work you're doing has implications for the bottom lineincreased revenues or reduced cost. Executives want their investment in your skills to deliver a solution that means increased profits. The term for this in financial circles is return on investment (ROI). However, the funny thing about this financial expectation is that some executives analyze the ROI for only a single project. A real return on investment should be measured across several software development projects. Executives should be looking for how a component developed in project A can be effectively reused in succeeding projects B, C, D, E, and so on. Reuse of components is like having a part of a project that pays for itself over and over again. Because reusable objects and components provide a lasting return on investment, they should be valued across many projects, not just one. The labor of a skilled developer (such as you) can be encapsulated in a reusable component and implemented repeatedly, providing diminishing costs. This line of thinking should be the basis of your discussion with curious managers and executives, should you ever be summoned to speak to them about the progress of your project. |
|
|
|
|
|